This folder contains a firmware program file called “PN357/377 Firmware 1.0.” This file contains the code that also stored in PN357 and PN377 StarControllers. You can try out the new reprogramming features of the PN357 and PN377 StarControllers with this file. This file is identical to the firmware already in all PN357 and PN377 StarControllers; reprogramming with this file will not change StarControllers functioning in any way.
For StarCommand 2.2.1 Users
--------------------------
This folder contains a utility application called “SC 2.2.1 File Converter.” This application reads in a “StarInfo” file created by StarCommand 2.2.1, and creates a new StarCommand 3.0 document out of it. It does not delete or change the original “StarInfo” file.
A Few Tips…
------------
StarCommand’s performance is related to how many things it tries to do at once. Leaving searching on slows StarCommand down slightly. Each additional hub in the device list also slows StarCommand down slightly. Trying to monitor 50 hubs all at once means that each hub will get 1/50th of StarCommand’s attention. To speed up StarCommand, omit StarControllers that you are not actively monitoring. Each open window adds to the information StarCommand must monitor, so closing unnecessary windows helps. For more tips, see Appendix B of the StarCommand User’s Guide, Power User Tips.
Avoid running multiple copies of StarCommand simultaneously. The increased management traffic causes communication problems which often cause hub statuses to go “Off Line.” Heavy communication problems may cause StarControllers to reset (and clear their counters). You can always see who is running StarCommand over the network by using CheckNET to look for a device with a “StarCommand” type.
StarCommand gives higher priority to the frontmost window. A Port List or Info Window will update the counters quicker if you bring it to the front.
StarCommand’s searching for PN207 StarControllers can take a long time in comparison to more recent hubs. StarCommand finds PN207 StarControllers in ascending numerical order, starting at address 240 (hexadecimal F0), then 241, then 242, and so on up to 254. It then starts looking at address 1, then 2, and so on. You can reduce the time StarCommand takes to find PN207 StarControllers by changing their addresses to the 240-254 range (hexadecimal F0-FE).
StarCommand may run out of memory on large networks (more than 30 hubs). Memory usage is roughly 375K + 10K per hub. Extended management hubs, and hubs with long comments may require a little more. You can change StarCommand’s memory allocation in the Finder by selecting the StarCommand file and choosing Get Info from the File menu.
Known Bugs
-----------
StarCommand isn’t perfect. A few bugs exist in this version:
• Icons in 16 greyscales—Selecting an icon on a screen set to 16 levels of greys will cause a “shadow” to appear around the icon.
• Line Tests on PN207s—StarCommand may occasionally hang if a StarCommand document is closed (or Quit is selected) while performing a line test on a PN207. Wait until the PN207 line test is complete before quitting or closing a file.
• Running StarCommand on a Portable with an internal modem—You must remove or disable the internal modem if you want StarCommand to communicate with StarControllers via the Modem Port.
